When 3.1g encounters scale .5*z it issues error
messages for x and y scale by 0 and informs us of scale
by 1 instead.

    OK, not a bug but this is inconsistant with
translate and rotate .5*z which do not issue error
messages.

    While we can see that that an assumed zero would
only result in a real problem for scale and not for
translate or rotate the assumption of shorthand should
exist in all three cases and error messages should be
consistant.

    I presume this goes to the parser which expands
.5*z to <0,0,.5> before looking at the what it is a
vector for. But if the error can be referred to a
correction from 0 to 1, certainly it can also flag the
error message as not emit.

Post a reply to this message